-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-12246: [CI] Sync conda recipes with upstream feedstock #9923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-12246: [CI] Sync conda recipes with upstream feedstock #9923
Conversation
|
@github-actions crossbow submit -g conda |
|
Revision: 83b91bf34161bcfef9c5449c2d9161fe80477233 Submitted crossbow builds: ursacomputing/crossbow @ actions-275 |
|
@github-actions crossbow submit conda-linux-gcc-py38-cpu |
|
Revision: 70a18ef102ef146c100865a30807f7d7875cb4ad Submitted crossbow builds: ursacomputing/crossbow @ actions-276
|
|
@github-actions crossbow submit conda-linux-gcc-py38-cpu |
|
Revision: 985951ee3eff85a713d4518441715a5732803ae0 Submitted crossbow builds: ursacomputing/crossbow @ actions-284
|
|
I suppose that in the past we made some adjustments to the build scripts ( |
|
Eg #4649 has some changes to that file after the initial commit adding it: https://github.com/apache/arrow/pull/4649/files/2037f78fc8a5842a123930656afe73f7a1e25cbb..20f6cecd3e8a8e476387a6441d6572ff94fa6e5f#diff-7ad035b7e05f08778571fe6908954a873b6ca24fe661324cb9d1a29c7c4e505b |
|
@jorisvandenbossche I would revert the changes to |
Sure! |
|
@github-actions crossbow submit conda-linux-gcc-py38-cpu |
|
Note that I have a large undertaking for crossbow #9913 which I plan to merge today, so expect for some minor conflicts. @xhochy Just an idea: could we |
I don't see any conflicting things here, so I would hope that a rebase here will work out fine. Thanks for the heads-up 👍
Yes, that could be part of a future solution. I'm currently struggling a bit with it though as the number of possible conda configurations varies on conda-forge and the names of the files in |
|
Revision: 91b780510a57150d89588b8cb7f9285a9683ff16 Submitted crossbow builds: ursacomputing/crossbow @ actions-291
|
|
@github-actions crossbow submit -g conda |
|
Revision: 82b5d5a1c685b90595e9ad013a7c7b341c527d2c Submitted crossbow builds: ursacomputing/crossbow @ actions-298 |
|
@github-actions crossbow submit conda-win-* |
|
Revision: 989900a7c56a05826195d18462e8fa79511d8e31 Submitted crossbow builds: ursacomputing/crossbow @ actions-301
|
|
@jorisvandenbossche @kszucs This is ready for review, updated all x86 conda packages and sneaked in builds for the Apple M1. |
|
One of the Windows builds progressed so far on my crossbow that I'm confident that the rest will also be green in ~1h: https://dev.azure.com/mail0406/crossbow/_build/results?buildId=26&view=logs&j=4c86bc1b-1091-5192-4404-c74dfaad23e7&t=41795ef0-6501-5db4-3ad4-33c0cf085626 |
989900a to
f337001
Compare
|
@github-actions crossbow submit -g conda |
|
Revision: f337001 Submitted crossbow builds: ursacomputing/crossbow @ actions-310 |
jorisvandenbossche
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for finishing this! Assuming the builds pass, this is all good for me.
I just added two suggestions of adding some more comments for our future selves (I commented on a subset of the diff, to see the changes after updating with the upstream version, but could be I was looking at wrong changes;)).
| copy /Y "%SRC_DIR%\cpp\cmake_modules\CompilerInfo.cmake" cmake_modules\ | ||
| copy /Y "%SRC_DIR%\cpp\cmake_modules\FindNumPy.cmake" cmake_modules\ | ||
| copy /Y "%SRC_DIR%\cpp\cmake_modules\FindPythonLibsNew.cmake" cmake_modules\ | ||
| @rem del cmake_modules\BuildUtils.cmake |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth adding a comment that those are commented out compared to the upstream conda-forge build script?
| @@ -1,6 +1,6 @@ | |||
| {% set version = "3.0.0" %} | |||
| {% set version = ARROW_VERSION %} | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe can add a comment here indicating that setting this to ARROW_VERSION is a difference compared to the upstream version?
(I am first trying with linux)